FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.7.16  |  FHIR Version n/a  User: [n/a]

Resource ValueSet/FHIR Server from package hl7.fhir.be.terminology#current (16 ms)

Package hl7.fhir.be.terminology
Type ValueSet
Id Id
FHIR Version R4
Source https://hl7belgium.org/profiles/fhir/terminology/https://build.fhir.org/ig/hl7-be/terminology/ValueSet-be-vs-allergyintolerance-type.html
Url https://www.ehealth.fgov.be/standards/fhir/allergy/ValueSet/be-vs-allergyintolerance-type
Version 1.0.0
Status active
Date 2023-12-18T12:02:54+01:00
Name BeVSAllergyIntoleranceType
Title BeVSAllergyIntoleranceType
Experimental False
Realm be
Authority hl7
Description Codes as communicated by NIHDI and the FOD Terminology Center differentiating types of allergy intolerance.

Resources that use this resource

StructureDefinition
https://www.ehealth.fgov.be/standards/fhir/allergy/StructureDefinition/be-ext-allergy-type BeExtAllergyType
https://www.ehealth.fgov.be/standards/fhir/allergy/StructureDefinition/be-model-allergyintolerance Allergy Intolerance Logical Model

Resources that this resource uses

CodeSystem
http://snomed.info/sct SNOMED CT (all versions)
http://snomed.info/sct Nutrition Care Process Terminology module
http://snomed.info/sct veri


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ValueSet be-vs-allergyintolerance-type


Source

{
  "resourceType" : "ValueSet",
  "id" : "be-vs-allergyintolerance-type",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet be-vs-allergyintolerance-type</b></p><a name=\"be-vs-allergyintolerance-type\"> </a><a name=\"hcbe-vs-allergyintolerance-type\"> </a><ul><li>Include these codes as defined in <a href=\"http://www.snomed.org/\"><code>http://snomed.info/sct</code></a><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td></tr><tr><td><a href=\"http://snomed.info/id/609328004\">609328004</a></td><td style=\"color: #cccccc\">Allergy</td></tr><tr><td><a href=\"http://snomed.info/id/609396006\">609396006</a></td><td style=\"color: #cccccc\">Pseudoallergic disposition</td></tr><tr><td><a href=\"http://snomed.info/id/782197009\">782197009</a></td><td style=\"color: #cccccc\">Intolerance to substance</td></tr><tr><td><a href=\"http://snomed.info/id/609433001\">609433001</a></td><td style=\"color: #cccccc\">Hypersensitivity disposition</td></tr></table></li></ul></div>"
  },
  "url" : "https://www.ehealth.fgov.be/standards/fhir/allergy/ValueSet/be-vs-allergyintolerance-type",
  "version" : "1.0.0",
  "name" : "BeVSAllergyIntoleranceType",
  "title" : "BeVSAllergyIntoleranceType",
  "status" : "active",
  "experimental" : false,
  "date" : "2023-12-18T12:02:54+01:00",
  "publisher" : "My Organization",
  "contact" : [
    {
      "name" : "My Organization",
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://example.com/committees"
        },
        {
          "system" : "email",
          "value" : "my-group@example.com"
        }
      ]
    },
    {
      "name" : "Bob Smith",
      "telecom" : [
        {
          "system" : "email",
          "value" : "bobsmith@example.com",
          "use" : "work"
        }
      ]
    }
  ],
  "description" : "Codes as communicated by NIHDI and the FOD Terminology Center differentiating types of allergy intolerance.",
  "jurisdiction" : [
    {
      "coding" : [
        {
          "system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code" : "001",
          "display" : "World"
        }
      ]
    }
  ],
  "compose" : {
    "include" : [
      {
        "system" : "http://snomed.info/sct",
        "concept" : [
          {
            "code" : "609328004"
          },
          {
            "code" : "609396006"
          },
          {
            "code" : "782197009"
          },
          {
            "code" : "609433001"
          }
        ]
      }
    ]
  }
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.